2027 Objectives Framework
The Cardano 2030 Strategy is structured around five strategic pillars, each divided into sections covering specific areas of ecosystem development (as well as example focus areas).
To support the 2027 Cardano budget process, committees are asked to identify and prioritise the outcomes that Cardano should achieve or make meaningful progress towards during 2027.
For each relevant 2030 Strategy section, committees should draft up to five candidate objectives (so on avg 2 per pillar section), with the aim of prioritising two to three.
How to define objectives
Objectives should define what Cardano needs to achieve in 2027, not what projects should be funded or how those projects should deliver it.
So objectives should be specific enough to be actionable and high level enough to not dictate how they are met.
What makes a good objective?
- Outcome-focused: Describe the improvement or change Cardano needs, not a deliverable or activity.
- Actionable: Be specific enough that people can develop proposals to achieve it.
- Solution-neutral: Allow different approaches and providers to compete or collaborate.
- Assessable: Make it possible to determine whether meaningful progress was achieved during 2027.
To avoid forcing artificial one-year targets onto strategic outcomes that may require several years of work two types of objectives can be proposed:
- Achievement objectives: An outcome that should be realised fully during 2027 (e.g. reducing onboarding friction)
- Progress objectives: A longer-term outcome toward which 2027 investment should deliver meaningful, demonstrable progress (e.g. increasing client diversity)
Objective Examples:
Pillar 2 (Adoption & Utility) - Section: A.2. Experience (Business & Consumer)
- Too broad: "Improve the Cardano user experience."
- Doesn't indicate which improvements matter or what progress should look like.
- Too prescriptive: "Develop a new wallet with social login and gasless transactions."
- Specifies a solution instead of the desired outcome.
- Good objective: "Reduce the complexity and friction of onboarding and transacting on Cardano for new users."
- Defines a clear improvement while allowing multiple approaches to achieve it.
Pillars / Committees / Stakeholders:
| Pillar | Committee | Stakeholders |
|---|---|---|
| Pillar 1 - Infrastructure & Research Excellence | CPC - TSC | Core protocol developers, infrastructure and L2 developers, research organizations, stake pool operators (SPOs), security specialists, infrastructure service providers, application developers and technical delivery partners. |
| Pillar 2 - Adoption & Utility | CPC - GMC | dApp builders, DeFi protocols, businesses and enterprises, wallet providers, exchanges, payment providers, stablecoin issuers, RWA platforms, developers, end users and institutional adopters. |
| Pillar 3 - Governance | CCC - TSC | DReps, ada holders and delegators, the Constitutional Committee, SPOs, governance tool providers, treasury applicants and recipients, Intersect members and the wider Cardano community. |
| Pillar 4 - Community & Ecosystem Growth | GMC - OSC | Community organizations, developers and contributors, educators, universities, regional ambassadors, ecosystem entrepreneurs, accelerators, marketing partners and local adoption partners. |
| Pillar 5 - Ecosystem Sustainability & Resilience | CBC - TSC | SPOs, ada holders and delegators, treasury and budget stakeholders, protocol economists, core developers, infrastructure providers, DeFi and L2 operators, DReps and ecosystem funding recipients. |
Pillars / Domains:
Pillars represent high-level goals, which are operationalised by subtracks or “domains” to split spending into distinct categories.
One domain can correspond, where appropriate, with multiple pillars. Proposals submitted shouldn’t be submitted under more than one domain to ensure that spending can be properly tracked. Objectives will be related to only one domain and one pillar.
| Domain | Domain Description |
|---|---|
| Core Development & Maintenance | Funds the work that keeps Cardano secure and running, from node development and maintenance to node diversity, critical dependencies, protocol upgrades, and research check-ins on specifications. |
| Applied Research | Funds the research that keeps Cardano secure, resilient and evolving: peer-reviewed research in areas like cryptography, consensus and scaling, which becomes the next generation of protocol features. |
| Developer Support | Funds the open-source tools, libraries, APIs, SDKs, dev infra and tooling, maintainer support and documentation etc. that make it faster and cheaper to build on Cardano. |
| Marketing, Analysis & Events | Funds how Cardano is marketed, where it shows up at industry events, and the market and on-chain analysis that shows whether that work pays off. |
| Adoption & Ecosystem Growth | Funds the partnerships, integrations and programs that bring real users, businesses and institutions onto Cardano. |
| Governance Coordination | Funds the shared infrastructure of on-chain governance: tooling, DRep and community education, and the processes that support the Constitution. |
| Domains | Related 2030 Pillars |
|---|---|
| Core Development & Maintenance Applied Research | Pillar 1 - Infrastructure & Research Excellence |
| Adoption & Ecosystem Growth | Pillar 2 - Adoption & Utility Pillar 4 - Community & Ecosystem Growth |
| Developer Support | Pillar 2 - Adoption & Utility |
| Governance Coordination | Pillar 3 - Governance |
| Marketing, Analysis & Events | Pillar 4 - Community & Ecosystem Growth |
| Open Contribution (Flexible portion of NCL allocated to new opportunities still requiring alignment to a pillar) | Any Pillars 1-5 |
2027 Objective Definition Template
Questions to answer for each objective
- Objective — What should improve in 2027?
- Why does it matter?
- How could we assess progress?
Illustrative completed example
Strategic alignment: Pillar 2 - Adoption & Utility - Section A.3: Developer Experience
- Objective — What should improve in 2027?
- Reduce the time and complexity required for developers to build and deploy applications on Cardano.
- Why does it matter?
- Developer friction limits Cardano's ability to attract builders, accelerate application development and increase ecosystem adoption.
- How could we assess progress?
- Reduced time to first successful deployment, higher developer satisfaction and improved developer retention.